getting my own IP back

Tue Feb 18 00:41:35 UTC 2003

Well, you messed up some of those "dig" command-lines, so some of those 
queries unexpectedly went to localhost.

But still, you and I are getting very strange results when we use 
209.173.210.166 for queries. It's as if it's getting all of the right 
information, except that all of the A records are changed to 
209.173.210.166 and a 0 TTL.

Is this something a firewall might be doing? Alternatively, do you have 
something odd in your named.ca file (perhaps some "alternate" root 
servers that might be doing strange things)?

                                                - Kevin

julianop wrote:

>Kevin, thanks a million for helping out.
>
>The wildcard in the MX came from my entry at granite canyon, which I built
>from their template. I copied that, essentially, into my own file.
>Here are responses:-
>>From nslookup:
>=================
>[root at anoka named]# nslookup -sil www.ipswitch.com 209.173.210.166
>Server:         209.173.210.166
>Address:        209.173.210.166#53
>
>Non-authoritative answer:
>Name:   www.ipswitch.com
>Address: 209.173.210.166
>Name:   www.ipswitch.com
>Address: 209.173.210.166
>=================
>>From dig:
>=================
>[root at anoka named]# dig www.ipswitch.com 209.173.210.166
>
>; <<>> DiG 9.1.3 <<>> www.ipswitch.com 209.173.210.166
>;; global options:  printcmd
>;; Got answer:
>;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15208
>;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 3, ADDITIONAL: 1
>
>;; QUESTION SECTION:
>;www.ipswitch.com.              IN      A
>
>;; ANSWER SECTION:
>www.ipswitch.com.       1918    IN      A       156.21.1.169
>www.ipswitch.com.       1918    IN      A       156.21.1.171
>
>;; AUTHORITY SECTION:
>ipswitch.com.           84718   IN      NS      hub.ipswitch.com.
>ipswitch.com.           84718   IN      NS      ns1.ipswitch.com.
>ipswitch.com.           84718   IN      NS      alpha.ipswitch.com.
>
>;; ADDITIONAL SECTION:
>ns1.ipswitch.com.       84718   IN      A       156.21.1.2
>
>;; Query time: 3 msec
>;; SERVER: 127.0.0.1#53(127.0.0.1)
>;; WHEN: Mon Feb 17 17:23:45 2003
>;; MSG SIZE  rcvd: 138
>
>;; Got answer:
>;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 42080
>;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
>
>;; QUESTION SECTION:
>;209.173.210.166.               IN      A
>
>;; AUTHORITY SECTION:
>..                       8384    IN      SOA     A.ROOT-SERVERS.NET.
>NSTLD.VERISIGN-G
>RS.COM. 2003021701 1800 900 604800 86400
>
>;; Query time: 1 msec
>;; SERVER: 127.0.0.1#53(127.0.0.1)
>;; WHEN: Mon Feb 17 17:23:45 2003
>;; MSG SIZE  rcvd: 108
>
>=================
>
>Here's what I get from dig if I use "localhost" as the server argument:
>=================
>; <<>> DiG 9.1.3 <<>> www.ipswitch.com localhost
>;; global options:  printcmd
>;; Got answer:
>;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16990
>;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 3, ADDITIONAL: 1
>
>;; QUESTION SECTION:
>;www.ipswitch.com.              IN      A
>
>;; ANSWER SECTION:
>www.ipswitch.com.       1847    IN      A       156.21.1.171
>www.ipswitch.com.       1847    IN      A       156.21.1.169
>
>;; AUTHORITY SECTION:
>ipswitch.com.           84647   IN      NS      hub.ipswitch.com.
>ipswitch.com.           84647   IN      NS      ns1.ipswitch.com.
>ipswitch.com.           84647   IN      NS      alpha.ipswitch.com.
>
>;; ADDITIONAL SECTION:
>ns1.ipswitch.com.       84647   IN      A       156.21.1.2
>
>;; Query time: 3 msec
>;; SERVER: 127.0.0.1#53(127.0.0.1)
>;; WHEN: Mon Feb 17 17:24:56 2003
>;; MSG SIZE  rcvd: 138
>
>;; Got answer:
>;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41458
>;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0
>
>;; QUESTION SECTION:
>;localhost.                     IN      A
>
>;; ANSWER SECTION:
>localhost.              86400   IN      A       127.0.0.1
>
>;; AUTHORITY SECTION:
>localhost.              86400   IN      NS      localhost.
>
>;; Query time: 2 msec
>;; SERVER: 127.0.0.1#53(127.0.0.1)
>;; WHEN: Mon Feb 17 17:24:56 2003
>;; MSG SIZE  rcvd: 57
>=================
>Finally, here are three calls to host:
>=================
>[root at anoka named]# host www.ipswitch.com
>www.ipswitch.com. has address 156.21.1.169
>www.ipswitch.com. has address 156.21.1.171
>[root at anoka named]# host www.ipswitch.com 209.173.210.166
>Using domain server:
>Name: 209.173.210.166
>Address: 209.173.210.166#53
>Aliases:
>
>www.ipswitch.com. has address 209.173.210.166
>www.ipswitch.com. has address 209.173.210.166
>[root at anoka named]# host www.ipswitch.com localhost
>Using domain server:
>Name: localhost
>Address: 127.0.0.1#53
>Aliases:
>
>www.ipswitch.com. has address 156.21.1.169
>www.ipswitch.com. has address 156.21.1.171
>=================
>
>Hope all this helps :-)
>j.
>=====================
>"Kevin Darcy" <kcd at daimlerchrysler.com> wrote in message
>news:b2rqce$1bnc$1 at isrv4.isc.org...
>  
>
>>Well, barnlea.com looks somewhat reasonable, except that a couple of the
>>MX targets aren't dot-terminated. Also, you shouldn't use a wildcard MX
>>unless you *fully* understand what it does to your MTA's routing and
>>addressing logic. Wildcard MX'es can have surprising side effects.
>>
>>What does a bad "dig" response look like?
>>
>>
>>    
>>
><clip>
>
>
>
>
>
>  
>