[dns-operations] 167.216.129.170 RDNS

Lyle Giese lyle at lcrcomputer.net
Thu Sep 11 13:13:10 UTC 2014


Another data point for you:

On Aug 28, I wrote this open message on the NANOG mailing list:

I discovered that NetSuite's dns servers ens0 & 1 .netsuite.com are 
invisible from Comcast's business services in the Chicago area(limits of 
my testing abilities) but I can reach these same servers from a Linode 
virtual system in the Dallas, TX area.

Looks like it's been this way for at least two months.

If someone from NetSuite could say hi and look into it, I am sure it 
will help NetSuite more than me.

Lyle Giese
LCR Computer Services, Inc.

I never heard back from anyone, but I can reach them today from my 
Comcast business connection in the Chicago area right now.


On 09/11/14 07:51, Dave Brockman wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hello All,
>    I am having difficulty resolving Reverse DNS for 167.216.129.170,
> and I'm not entirely certain why.  If I just do a dig -x
> 167.216.129.170 I get:
>
> ; <<>> DiG 9.7.3 <<>> -x 167.216.129.170
> ;; global options: +cmd
> ;; connection timed out; no servers could be reached
>
>
> If I dig -x +trace 167.216.129.170:
>
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 28671
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
>
> ;; QUESTION SECTION:
> ;167.216.129.170.               IN      A
>
> ;; AUTHORITY SECTION:
> .                       10549   IN      SOA     a.root-servers.net.
> nstld.verisign-grs.com. 2014091100 1800 900 604800 86400
>
>
> and finally, if I  dig -x 167.216.129.170 @8.8.8.8:
>
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58383
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
>
> ;; QUESTION SECTION:
> ;170.129.216.167.in-addr.arpa.  IN      PTR
>
> ;; ANSWER SECTION:
> 170.129.216.167.in-addr.arpa. 3047 IN   CNAME
> 170.0-24.129.216.167.in-addr.arpa.
> 170.0-24.129.216.167.in-addr.arpa. 3047 IN PTR  nmail2.netsuite.com.
>
>
> This is impacting my ability to receive transactional emails from this
> IP address in particular.  My DNS server is running Bind 9.7.3 on
> Debian Squeeze.  I thought perhaps my DNS server was being blocked,
> but that wouldn't explain the NXDOMAIN I don't believe.  I apologize
> in advance if this is something simple and/or obvious, but can anyone
> explain what is happening and/or how to correct it?  Many thanks in
> advance!
>
> Regards,
>
> dtb
>
> Dave Brockman
> Senior Network Engineer
>
>
> - -- 
> "Some things in life can never be fully appreciated nor understood
> unless experienced firsthand. Some things in networking can never be
> fully understood by someone who neither builds commercial networking
> equipment nor runs an operational network." RFC 1925
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.17 (MingW32)
>
> iQEcBAEBAgAGBQJUEZrqAAoJEMP+wtEOVbcdBFcH/jS+6PLbOG7pGXSlxZJ5XFMi
> l4GC1kF/ukrwh4wzUr2kKOXpBnO0H9DPMOpJN4TG2ABNDrfubciMNtKXLQCw33jU
> U/v3OiBv9LlziKZ+keD8Fg1dTKTUM74rIkCtN8LzkQT0eGeBj53nnAG+Q/8kMefF
> 7MlmM6SPZYd7NxrCSgs2jO/Y5hXnIOKh8FRPhOKU5vou+iKbOPp+Uuvi4drozhXZ
> 2iGOQ/mwo79SaGynHNTZeo6zjOR9U5W5zH8TdVZz//589lvtqIdybjOzfuQmXo+G
> 7e+yzvKw9dl2frf59+2jMVKKQ2LAyyAMKcrwIU8SyzglyMNNlwSv01Abuo+89jg=
> =YaMy
> -----END PGP SIGNATURE-----
> _______________________________________________
> dns-operations mailing list
> dns-operations at lists.dns-oarc.net
> https://lists.dns-oarc.net/mailman/listinfo/dns-operations
> dns-jobs mailing list
> https://lists.dns-oarc.net/mailman/listinfo/dns-jobs




More information about the dns-operations mailing list