nameserver spoiling avahi multicast name resolution of .local domain

Posted by Doug Coburn on Super User See other posts from Super User or by Doug Coburn
Published on 2012-03-25T02:53:59Z Indexed on 2012/03/25 5:33 UTC
Read the original article Hit count: 511

Filed under:
|
|

After trying to ping a machine on my local network, I noticed that I was trying hit address 66.152.109.24. This is an external public address. Resolution should have occurred via avahi mDNS. I ran dig to see how the name resolution worked and my quest/centurylink name server was retuning results for my .local domain queries! I tried a random name and got the same ip address result.

 $ dig jakdafj.local

 ; <<>> DiG 9.8.1-P1-RedHat-9.8.1-3.P1.fc15 <<>> jakdafj.local
 ;; global options: +cmd
 ;; Got answer:
 ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58410
 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

 ;; QUESTION SECTION:
 ;jakdafj.local.            IN  A

 ;; ANSWER SECTION:
 jakdafj.local.     10  IN  A   66.152.109.24
 jakdafj.local.     10  IN  A   204.232.231.46

 ;; Query time: 104 msec
 ;; SERVER: 205.171.3.25#53(205.171.3.25)
 ;; WHEN: Sat Mar 24 20:40:17 2012
 ;; MSG SIZE  rcvd: 63

Am I missing something or is my DNS name server at 205.171.3.25 corrupted?

© Super User or respective owner

Related posts about dns

Related posts about isp