IP Whitelist Denied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
We have had a whitelisting request for one of our IP addresses denied, it appears that you may have the rDNS for the IP in question cached as the rDNS is indeed configured:
dig +trace ptr 214.22.126.209.in-addr.arpa ; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.47.rc1.el6_8.4 <<>> +trace ptr 214.22.126.209.in-addr.arpa ;; global options: +cmd . 514516 IN NS i.root-servers.net. . 514516 IN NS a.root-servers.net. . 514516 IN NS d.root-servers.net. . 514516 IN NS g.root-servers.net. . 514516 IN NS j.root-servers.net. . 514516 IN NS f.root-servers.net. . 514516 IN NS m.root-servers.net. . 514516 IN NS b.root-servers.net. . 514516 IN NS k.root-servers.net. . 514516 IN NS l.root-servers.net. . 514516 IN NS c.root-servers.net. . 514516 IN NS h.root-servers.net. . 514516 IN NS e.root-servers.net. ;; Received 228 bytes from 208.67.222.222#53(208.67.222.222) in 125 ms in-addr.arpa. 172800 IN NS c.in-addr-servers.arpa. in-addr.arpa. 172800 IN NS a.in-addr-servers.arpa. in-addr.arpa. 172800 IN NS e.in-addr-servers.arpa. in-addr.arpa. 172800 IN NS d.in-addr-servers.arpa. in-addr.arpa. 172800 IN NS f.in-addr-servers.arpa. in-addr.arpa. 172800 IN NS b.in-addr-servers.arpa. ;; Received 421 bytes from 199.7.91.13#53(199.7.91.13) in 208 ms 209.in-addr.arpa. 86400 IN NS y.arin.net. 209.in-addr.arpa. 86400 IN NS arin.authdns.ripe.net. 209.in-addr.arpa. 86400 IN NS u.arin.net. 209.in-addr.arpa. 86400 IN NS x.arin.net. 209.in-addr.arpa. 86400 IN NS r.arin.net. 209.in-addr.arpa. 86400 IN NS z.arin.net. ;; Received 165 bytes from 199.212.0.73#53(199.212.0.73) in 85 ms 22.126.209.in-addr.arpa. 86400 IN NS ns1.nexcess.net. 22.126.209.in-addr.arpa. 86400 IN NS ns4.nexcess.net. 22.126.209.in-addr.arpa. 86400 IN NS ns3.nexcess.net. 22.126.209.in-addr.arpa. 86400 IN NS ns2.nexcess.net. ;; Received 128 bytes from 199.212.0.63#53(199.212.0.63) in 120 ms 214.22.126.209.in-addr.arpa. 43200 IN PTR speedee.nexcess.net. ;; Received 78 bytes from 207.32.191.58#53(207.32.191.58) in 3 ms
Can we please revisit this request?
-Hanson
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi technex,
Your issue has been escalated to a Verizon agent. Before the agent can begin assisting you, they will need to collect further information from you. Please go to your profile page for the forum and scroll down the page to an area titled "My Support Cases". You can reach your profile page by clicking on your name located above your post, or at the top right of this page.
Under "My Support Cases" you will find a link to the private board where you and the agent may exchange information. The title of your post is the link. This should be checked on a frequent basis, as the agent may be waiting for information from you before they can proceed with any actions. To ensure you know when they have responded to you, you may subscribe to the case. At the top right of your support case there is a gear icon which provides a drop down menu with support case options. Click that and choose "subscribe". Please keep all correspondence regarding your issue in the private support portal.
