Norton DNS and dns forwarding

Archive
1

Seems like the new IP's are not acting as authoratative servers for my local cache dns servers when I try and set up forwarding to the 199.85.126.30 or 199.85.127.30 IP's.  (The old IP's worked)  I can change my local PC dns and use the new IP's successfuly, but I have a split dns that requires me to run my own small dns servers.

 

Why the significant change and lack of communication to the community.  I work at a non-profit which falls within your allowed business model for using Norton DNS.  If you are trying to prevent business's that fall outside of what you intend to provide service for, then at least give those of us who really do qualify as a small business or non-profit a chance to use the service as it was orginally setup.  

2

Hi, cthim.

 

It seems that you're not alone.  There's another thread discussing this very problem.  See here: https://community.norton.com/t5/Other-Norton-Products/Norton-DNS-new-IP-s-not-working/td-p/1079013

3

The problem reported in the link you reference seems to be a different issue than what I am reporting.

4

Hi cthim,

 

Thanks for the post.  Can you please let us know where you are located, in the US, which state?

 

 

Thanks,

Katie

5

I am located in Texas about an hour NW of San Antonio.

6

Now the old IP's and the new IP's simply provide recursive service and are NOT preventing anything from being accessed when in use as forwading servers for dns.  Are you guys treating tcp/udp traffic differently maybe?

7

So it seems like the new IP's from Norton are honoring dns forwarding requests from microsoft dns with recursive lookup results instead of interative lookup results.  This behaviour change is really damaging for us that were quite happy with the way things used to be.  Does Norton have a recommendation for those of us who need our own dns servers but want to use Norton DNS as a forwarding resource for our dns servers?

8

Hi,

 

The same nodes that serve 199.xx also serve 198.xxx, so we shouldn't see a difference at all here. 

 

The 'old IS' starting with 198.xx are exactly the same as the 199.xxx IPs.  The 19.xxx set will continue to work and will not be retired.  Please use the 198.xx set.

 

 

Thanks,

Katie

9

We are not seeing a difference in the behavior of the IP's for 199.xxx.xxx.xxx vs 198.xxx.xxx.xxx.  They are all broke, not to worry I have transitioned off of your service for dns forwarding service, problem solved for me.