First-hand video of a BRS deployment.

Do you know what DNS stands for? It's Domain Name Server. In other
words, it is a server at your ISP that translates nemonic web addresses
into IP addresses. For example, you type http://www.dnsexample.com into
your address bar and the DNS translates that into something like
192.34.76.2. So if you are getting DNS errors the DNS at your ISP is
defective or not getting updates correctly from the network.

Scott


Mxsmanic wrote:

Scott writes:


Afraid of the French? Another person chimed in that he had no trouble
getting to their website from a different foreign country. I'd check
with your ISP and see if they have a range of IP addresses blocked.


It's not my ISP. The routing is being blocked, and so is DNS traffic.


Maybe THEY'RE afraid of the USAF! Just to double check, is this the
address you used: http://www.af.mil/


Anything with af.mil in it fails to work.

Scott writes:

Do you know what DNS stands for? It's Domain Name Server. In other
words, it is a server at your ISP that translates nemonic web addresses
into IP addresses. For example, you type http://www.dnsexample.com into
your address bar and the DNS translates that into something like
192.34.76.2. So if you are getting DNS errors the DNS at your ISP is
defective or not getting updates correctly from the network.

No. I run my own DNS nameserver, and it does not query the ISP's server (the
ISP's server is unreliable). If it cannot find a domain it will go all the
way back to the root servers, like most nameservers.

--
Transpose mxsmanic and gmail to reach me by e-mail.

So where do you get updates on domain names from? Without that, your
packets should go to some default server somewhere. Maybe the problem
lies with THAT server, wherever it is. Do you have a router running on
your system with any sort of firewall? Like I said before, take a trip
to your local library or internet cafe and check to see if you can get
to the site from there. So far, it doesn't sound like you've done any
outside troubleshooting. All you say is "It ain't my stuff that's bad."

So until you do, most here won't take your complaint too seriously
(myself included)...





Mxsmanic wrote:

Scott writes:


Do you know what DNS stands for? It's Domain Name Server. In other
words, it is a server at your ISP that translates nemonic web addresses
into IP addresses. For example, you type http://www.dnsexample.com into
your address bar and the DNS translates that into something like
192.34.76.2. So if you are getting DNS errors the DNS at your ISP is
defective or not getting updates correctly from the network.


No. I run my own DNS nameserver, and it does not query the ISP's server (the
ISP's server is unreliable). If it cannot find a domain it will go all the
way back to the root servers, like most nameservers.

Scott writes:

So where do you get updates on domain names from?

Since I have a nameserver, the updates come directly from the authoritative
name servers for each domain, in real time.

Without that, your packets should go to some default server somewhere.

They don't go anywhere if the DNS cannot resolve the name.

Maybe the problem lies with THAT server, wherever it is.

I can't reach the servers with direct IP addressing, either.

Do you have a router running on your system with any sort of firewall?

Yes. But there is nothing in the firewall that says "exclude Air Force
traffic."

--
Transpose mxsmanic and gmail to reach me by e-mail.

I understand that. But you don't have a range of IP addresses blocked
in which the USAF site might be in do you?



Mxsmanic wrote:

Scott writes:



Do you have a router running on your system with any sort of firewall?


Yes. But there is nothing in the firewall that says "exclude Air Force
traffic."

Scott writes:

I understand that. But you don't have a range of IP addresses blocked
in which the USAF site might be in do you?

I don't have any ranges blocked.

--
Transpose mxsmanic and gmail to reach me by e-mail.

Then why do you have a firewall? What does it do for you?



Mxsmanic wrote:

Scott writes:


I understand that. But you don't have a range of IP addresses blocked
in which the USAF site might be in do you?


I don't have any ranges blocked.