[dns-operations] 167.216.129.170 RDNS

[Dave Brockman]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thank you, and thank you Mark for reminding me to start my coffee :)

Regards,

dtb

On 9/11/2014 9:13 AM, Lyle Giese wrote:
> 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: 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
>> _______________________________________________ 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
> 
> _______________________________________________ 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

- -- 
"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)

iQEcBAEBAgAGBQJUEaRIAAoJEMP+wtEOVbcdvc8H/Aj9kiGxGt3ax1sI2KyAE2Tx
PkiYiBPHkdveS7nSjXZzDEVSa2JexdzKqa9stFNwFXMDqUvJU1/IGGxYBVpbHl1M
v4XRZmcJ2v+lVHo6ZUD8JL1gSYRkY0UvUcuKeL9+vTj8nBxSWGwb+ravIrFjpcDf
35cSntJ8ZcmC5VX9WA2I3GrVJPwEMR5bPwzTM/swFk4kCiV8vYnFhMAngyABYAAb
CD2PJT7vaf96Ul3oAiwKNXM/fJIFS39zsO3S/A/bloxNVU9rbPZYCWmhhRmbAWNX
51+zoEzprljBp1qI1/nh5NNsLEal0Yyh/6sRiQJoiHIdhAqZ4c/y2ONaRd0nBJk=
=3Tgr
-----END PGP SIGNATURE-----