Topic 'DNS problems?' in forum 'AT&T Southeast' - dslreports.com http://www.dslreports.com/forum/DNS-problems-3528775 en Fri, 25 Mar 2022 10:38:57 EDT Fri, 25 Mar 2022 10:38:57 EDT Re: DNS problems? http://www.dslreports.com/forum/Re-DNS-problems-3603504 http://www.dslreports.com/forum/Re-DNS-problems-3603504 Tue, 18 Jun 2002 22:20:59 EDT Re: DNS problems? http://www.dslreports.com/forum/Re-DNS-problems-3600051
As I said, the local servers are now closed off to the public at large and the only way to do that is thru ACLs. If your IP isn't in these ACLs, then no DNS service for you. You'll be cascaded down to a secondary which hopefully will still be open to the world. If not, you're dead in the water until you either take matters into your own hands or draw a new IP that is in the ACLs.]]> http://www.dslreports.com/forum/Re-DNS-problems-3600051 Tue, 18 Jun 2002 16:24:10 EDT Re: DNS problems? http://www.dslreports.com/forum/Re-DNS-problems-3599728 http://www.dslreports.com/forum/Re-DNS-problems-3599728 Tue, 18 Jun 2002 15:53:19 EDT Re: DNS problems? http://www.dslreports.com/forum/Re-DNS-problems-3532308
Sure, DNS should work properly, and of course you'd want to know when it's not. So he posted.

Here's an observation for you.

It appears that you have now configured some or maybe all of the local DNS servers to reject queries from those not within your netblocks. Nothing wrong with this, other than you now must properly maintain the ACLs. Turning up new netblocks before the DNS server ACLs contain those new netblocks will be a problem.

So far the two servers in ATL remain globally open to resolution, so as long as you cascade customers down to those as secondaries, they won't be broken while the local server ACLs are caught up over time.]]> http://www.dslreports.com/forum/Re-DNS-problems-3532308 Tue, 11 Jun 2002 10:34:43 EDT Re: DNS problems? http://www.dslreports.com/forum/Re-DNS-problems-3532074
I did read your paste and see where you did not resolve, as your post indicated. However, this does not rule out another issue within the BHM BMF/CO.

> server 207.203.159.252
Default Server: ns.bhm.bellsouth.net
Address: 207.203.159.252

> www.dslreports.com
Server: ns.bhm.bellsouth.net
Address: 207.203.159.252

Non-authoritative answer:
Name: dslreports.com
Address: 209.123.109.175
Aliases: www.dslreports.com

quote:
205.152.0.5 is historically not a real good performer, being authoritative for the bellsouth.net domain and always under high load.

205.152.0.5 is a backup, people do not necessarily use or view it as such and use it incorrectly as primary or "their choice."

quote:
If you are going to accept PPP assigned DNS servers, then you get to take any and all problems that come with them. You may want to find others, or even run your own.

I do not agree with this statement, DNS should work properly as assigned by us, if not, we should know about it and correct the problem.

Shayne Causey
BSIS TSG Analyst]]> http://www.dslreports.com/forum/Re-DNS-problems-3532074 Tue, 11 Jun 2002 10:00:07 EDT Re: DNS problems? http://www.dslreports.com/forum/Re-DNS-problems-3531880 http://www.dslreports.com/forum/Re-DNS-problems-3531880 Tue, 11 Jun 2002 09:25:10 EDT Re: DNS problems? http://www.dslreports.com/forum/Re-DNS-problems-3531381
Thanks again!
hyper
--
Hey y'all... Watch this!]]> http://www.dslreports.com/forum/Re-DNS-problems-3531381 Tue, 11 Jun 2002 07:31:36 EDT Re: DNS problems? http://www.dslreports.com/forum/Re-DNS-problems-3531262
There have been no DNS troubles, nor alarms from our Network Management System worked in Birmingham (BHM) by the NOC, or Systems Operations. A quick check this morning reveals all DNS systems working properly.

Keep in mind other "network" related issues could be mask as DNS problems, as can a network card in a PC without an IP address associated with it, read "Stalls & Freezes". Check out the forum FAQ.

I would not recommend populating "other" city DNS codes such as was posted in this topic.

As a side note, if DNS is not working for one customer in BHM, for example, it will not be working for thousands of customers. Hence a "major" outage.

Shayne Causey
BSIS TSG Analyst
[text was edited by author 2002-06-11 06:31:06]
]]> http://www.dslreports.com/forum/Re-DNS-problems-3531262 Tue, 11 Jun 2002 06:29:23 EDT Re: DNS problems? http://www.dslreports.com/forum/Re-DNS-problems-3531211
Default Server: ns1.mia.bellsouth.net
Address: 205.152.144.235

I live in Fort Lauderdale and this one works fine. See what your ping times are to this one.]]> http://www.dslreports.com/forum/Re-DNS-problems-3531211 Tue, 11 Jun 2002 05:58:36 EDT Re: DNS problems? http://www.dslreports.com/forum/Re-DNS-problems-3528992 http://www.dslreports.com/forum/Re-DNS-problems-3528992 Mon, 10 Jun 2002 22:17:56 EDT Re: DNS problems? http://www.dslreports.com/forum/Re-DNS-problems-3528919 said by graysonf:

*** ns.bhm.bellsouth.net can't find www.dslreports.com: Query refused


graysonf,

Thanks for the quick check. The above refusal is exactly what's overtaken my system logs today. However, this is a new issue for me. I've been using the ISP assigned DNSs for about 9 months with absolutely no problems.

So... anyone know what's up with the server above?

Later...
hyper
--
Hey y'all... Watch this!]]> http://www.dslreports.com/forum/Re-DNS-problems-3528919 Mon, 10 Jun 2002 22:09:50 EDT Re: DNS problems? http://www.dslreports.com/forum/Re-DNS-problems-3528863 server 207.203.159.252
Default Server: ns.bhm.bellsouth.net
Address: 207.203.159.252

> www.dslreports.com
Server: ns.bhm.bellsouth.net
Address: 207.203.159.252

*** ns.bhm.bellsouth.net can't find www.dslreports.com: Query refused

205.152.0.5 is historically not a real good performer, being authoritative for the bellsouth.net domain and always under high load.

If you are going to accept PPP assigned DNS servers, then you get to take any and all problems that come with them. You may want to find others, or even run your own.]]> http://www.dslreports.com/forum/Re-DNS-problems-3528863 Mon, 10 Jun 2002 22:04:28 EDT DNS problems? http://www.dslreports.com/forum/DNS-problems-3528775
For me, the primary DNS supplied via PPP login is 207.203.159.252. All I've been able to get from this server this evening is rejects. The secondary DNS supplied is 205.152.0.5. This one works most of the time, but times out on a query about every 4 or 5 minutes. This results in about a 25 second stall. This problem just started for me today with no changes in setup or software. Any thoughts?

TIA,
hyper
--
Hey y'all... Watch this!]]> http://www.dslreports.com/forum/DNS-problems-3528775 Mon, 10 Jun 2002 21:56:55 EDT