×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Jobs

URI contains invalid FQDN. DNS resolved address does not match the Interface address

URI contains invalid FQDN. DNS resolved address does not match the Interface address

URI contains invalid FQDN. DNS resolved address does not match the Interface address

(OP)
I have a server edition.
I'm trying to convert an url to the IP address of the system.
To start the test, I created a line in Windows \ System32 \ Drivers \ etc \ hosts such that :

CODE

192.168.10.1 system.name.local 

When I go to URL https://system.name.local, I get this error :

CODE

URI contains invalid FQDN. DNS resolved address does not match the Interface address 

I have added name.local to DNS domain inside system DNS, without any changes.

Also, if I go to https://192.168.10.1, I access to the IP Office Select R11.0.4.1 page with Avaya logo

Do you have an idea to solve this problem?

RE: URI contains invalid FQDN. DNS resolved address does not match the Interface address

Is the server hostname system.name.local ?

"Trying is the first step to failure..." - Homer

RE: URI contains invalid FQDN. DNS resolved address does not match the Interface address

(OP)
Would you say the system name ?

RE: URI contains invalid FQDN. DNS resolved address does not match the Interface address

I have a suspicion that the IP Office itself is applying its own DNS checks to the requested address as a process of validation. Probably an anti-spoofing steps for phone registration and SIP calls.

Added my system as system.acme.com 192.168.0.1 in the host file.

Browsing to that has a few seconds pause before it comes back with the failure you see.

Removed the address of my networks DNS server from the IP Office system's own configuration. Now the failure message comes back immediately.

Various other tests but summary was that when connecting to any of my IP Offices, the hostname/address pair in the hosts file only worked when it was matched by the same hostname and IP address in the settings of my DNS server.

Playing the same game with a non-IP Office destination was no problem. I could route system.acme.com to a web server based in the hosts file, with or without system.acme.com being setup on the DNS server.









Stuck in a never ending cycle of file copying.

RE: URI contains invalid FQDN. DNS resolved address does not match the Interface address

(OP)
sizbut, Thank you for your answer.

I took several days to understand the overall meaning. Do you have an example when you say :

Quote (sizbut)

the hostname/address pair in the hosts file only worked when it was matched by the same hostname and IP address in the settings of my DNS server.

RE: URI contains invalid FQDN. DNS resolved address does not match the Interface address

Yeah, I ran into that in my IPO lab.

I think what sizbut means - and certainly what I've encountered - is suppose I have ipo.lab.com = 192.168.42.1 but I don't have it in my DNS server but i have it in my hosts file.

If I punch in http://192.168.42.1/46xxsettings.txt in my browser, the IPO will serve the file. If I punch http://ipo.lab.com/46xsettings.txt in my browser, the IPO will return that error because the IPO cares about the difference between FQDN and IP address and it needs to be able to lookup ipo.lab.com to be sure it's referring to itself.

RE: URI contains invalid FQDN. DNS resolved address does not match the Interface address

It should be fine if the actual hostname of the IP Office is ipo.lab.com.

Setting up a new lab for developing an app so gonna try it there.

"Trying is the first step to failure..." - Homer

RE: URI contains invalid FQDN. DNS resolved address does not match the Interface address

(OP)
Hmmm ok, I understand.
So, I'm looking for a workaround.

In your opinion, would it be possible to directly modify the `/etc/hosts` as root on the linux of the IPO (ssh)?

And add something like that :
(according to the syntax provided in this page)

CODE

192.168.10.1    system.name.local    system 

RE: URI contains invalid FQDN. DNS resolved address does not match the Interface address

Well, just tested it.

It doesn't work using the actual hostname or putting it in the hosts file of the Server Edition.

Don't have a DNS server in that environment at the moment so have to test that later.

"Trying is the first step to failure..." - Homer

RE: URI contains invalid FQDN. DNS resolved address does not match the Interface address

(OP)
:) Thanks
I've changed the hostname using interface :7071 > system > host name and this has changed the /etc/hosts file,
But without any benefic effects ...

RE: URI contains invalid FQDN. DNS resolved address does not match the Interface address

IIRC, that didn't work when I labbed it out at home - just a hosts file entry on the server edition. I ended up running Mara DNS on my laptop. It's a light fairly simple DNS server if you google up some examples and when the IPO used that and resolved itself I got it serving files.

RE: URI contains invalid FQDN. DNS resolved address does not match the Interface address

Won't be able to test any further til Friday but first thing I would do is point system monitor at it and use Service | DNS to see if, as I suspect, the IP Office is verifying the address used to route to it.

Stuck in a never ending cycle of file copying.

RE: URI contains invalid FQDN. DNS resolved address does not match the Interface address

To resolve this point the IPO DNS setting at a DNS server that resolves system.name.local to 192.168.10.1 and you should be good to go. The IP Office will check DNS to make sure the URI resolves to itself. I had this issue when a customer change the IP Office DNS to Google's 8.8.8.8. It worked OK from outside their network but failed with this error on their internal network, once we put it back to their internal DNS Server it worked.

“Some humans would do anything to see if it was possible to do it.
If you put a large switch in some cave somewhere, with a sign on it saying 'End-of-the-World Switch. PLEASE DO NOT TOUCH'.
The paint wouldn't even have time to dry.”

Terry Pratchet

RE: URI contains invalid FQDN. DNS resolved address does not match the Interface address

Even if it is a pretty bad workaround... The Linux server can have a hosts file as well

IP Office remote service https://www.fwilke.com/home
Fixed price SIP trunk configuration: https://www.fwilke.com/en/ip-office-sip-trunk-en/
CLI based cale blocking: https://blog.fwilke.com/ip-office-block-calls-from...
SCN fallback over PSTN: https://blog.fwilke.com/ip-office-scn-fallback/

RE: URI contains invalid FQDN. DNS resolved address does not match the Interface address

It does, but putting it there does nothing.

The web server is built into the ipoffice process so I guess it only looks at the DNS server defined in it's configuration.

"Trying is the first step to failure..." - Homer

RE: URI contains invalid FQDN. DNS resolved address does not match the Interface address

Also watch out for server reboots!

If the DNS settings in the Server is different to those in the IP Office config and the server reboots, the IP Office config settings are overwritten with the Server settings.

Caught us out that did :(

“Some humans would do anything to see if it was possible to do it.
If you put a large switch in some cave somewhere, with a sign on it saying 'End-of-the-World Switch. PLEASE DO NOT TOUCH'.
The paint wouldn't even have time to dry.”

Terry Pratchet

RE: URI contains invalid FQDN. DNS resolved address does not match the Interface address

You can put a DNS server out of your office to resolve internal addresses :

Create an account in Dynu.com (its free). Create a DDNS entry. for example yourname.dynu.net. You will see that the IP addr is the public you have. Change it and type the internal IP addr you need.

When typing yourname.dynu.net inside your network it will resolve it and give the ip you set up.

Regards.

RE: URI contains invalid FQDN. DNS resolved address does not match the Interface address

So as promised, some testing with system monitor set to trace DNS requests by the IP Office.

With DNS switched off (and now I know how upset a Windows server gets when it can get DNS responses) and DNS not set in the IP Office config, we see nothing in monitor (no surprise, it has nowhere to go) and no response in the browser.

With DNS set in the IP Office but DNS server still off - we see the IP Office make its request to verify the address and then the invalid FQDN response in the browser.

With DNS set in the IP Office and the DNS server back on (phew) - we see quite a long conversation (see below) where the IP Office queries both the DNS servers authority for the domain and then 2 requests validating the FQDN used to access the IP Office.

Conclusion: Name access to the IP Office only works if the system is configured with a DNS server and that DNS server validates the name.

Question: Why do you want name access when, if we find a workaround for your PC other than installing a local DNS, it will only work for your PC?

07:25:18     277442mS PRN: Monitor Status  S-Edition Primary Select 11.0.4.1.0 build 11
 07:25:18     277442mS PRN: Linux Whoo
 07:25:22     281347mS PRN: IPOKeepaliveTask::Main sending keepalives at 5000 ms
 [color #EF2929]07:25:23     282039mS DNS: Local Query example.com to 192.168.0.50
 07:25:23     282040mS DNS: Local Response example.com result=8580:questions=1,answer RRs=0,authority RRs=1,additional RRs=0
 07:25:23     282964mS DNS: Local Query storm1.example.com to 192.168.0.50
 07:25:23     282964mS DNS: Local Response storm1.example.com result=8580:questions=1,answer RRs=1,authority RRs=1,additional RRs=1
 07:25:23     282964mS DNS: RR: QType=0001 QClass=0001 ttl=86400 name=storm1.example.com target= ipaddr=192.168.0.180 
 07:25:23     282964mS DNS: AUTH: QType=0002 QClass=0001 ttl=86400 name=example.com target=dns.example.com ipaddr=0.0.0.0 
 07:25:23     282965mS DNS: ADD: QType=0001 QClass=0001 ttl=86400 name=dns.example.com target= ipaddr=192.168.0.50 
 07:25:24     283635mS DNS: storm1.example.com DNS - refreshing: have valid (not used) result
 07:25:24     283884mS DNS: Local Query storm1.example.com to 192.168.0.50
 07:25:24     283884mS DNS: Local Response storm1.example.com result=8580:questions=1,answer RRs=1,authority RRs=1,additional RRs=1
 07:25:24     283884mS DNS: RR: QType=0001 QClass=0001 ttl=86400 name=storm1.example.com target= ipaddr=192.168.0.180 
 07:25:24     283884mS DNS: AUTH: QType=0002 QClass=0001 ttl=86400 name=example.com target=dns.example.com ipaddr=0.0.0.0 
 07:25:24     283884mS DNS: ADD: QType=0001 QClass=0001 ttl=86400 name=dns.example.com target= ipaddr=192.168.0.50 
 07:25:25     284635mS DNS: storm1.example.com DNS - refreshing: have valid (not used) result 

Stuck in a never ending cycle of file copying.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close