PDA

View Full Version : Server 2008 - New DNS Servers - some sites cant be viewed?


Mr.Guvernment
07-13-09, 03:18 PM
I have set up 2 Domain controllers with AD and DNS (DC01 and DC02)

Now if i set my desktop system to use either DNS server, some websites, well 1 specifically, cant be viewed, IE seems to instantly say:


Internet Explorer cannot display the webpage

What you can try:
Diagnose Connection Problems

More information

This problem can be caused by a variety of issues, including:

•Internet connectivity has been lost.
•The website is temporarily unavailable.
•The Domain Name Server (DNS) is not reachable.
•The Domain Name Server (DNS) does not have a listing for the website's domain.
•There might be a typing error in the address.
•If this is an HTTPS (secure) address, click Tools, click Internet Options, click Advanced, and check to be sure the SSL and TLS protocols are enabled under the security section.




This is a default installation of a DNS server, no changes or modifications have been done to it, so far it only does this with 1 single website, all other sites work perfectly fine... I have tried it on 3 different computers all with the same result.

any thoughts?

SuperMiguel
07-13-09, 03:22 PM
when you set i up, when i asked you "Should this dns server forward queries, what you put?

Mr.Guvernment
07-13-09, 03:34 PM
i think ijust figured it out...

fictional names...


my DC controllers i set it up with the domain

ocfkicksbutt.com


now the website i am trying to view is

ocfkicksbutt.com

i assume the DNS records have the system pointing to it's self?

So i assume i need to set up my domain controller with a domain name other then that of an actual website that is up and running?



i just used AD installer, installed DNS, checked it off and that was it, dont recall it asking me if i want to forward requests

bchur83
07-13-09, 03:58 PM
Yeah, that would do it. By default it looks to itself for inquiries to its own domain. Usually with a local domain, you would use something like ocfkicksbutt.local for the domain. That way you dont have this problem.

Mr.Guvernment
07-13-09, 05:13 PM
ya, redoing it now with .local instead :)

i love learning as you go! glad i found this out now before deploying this new system in about 3 weeks!

bchur83
07-13-09, 05:29 PM
I made the same mistake once and learned from the error. I once found out about the error after going live with the server in a small office environment, then running into trouble with them accessing their company website.

mbentley
07-13-09, 08:32 PM
what i do with my domain (mbentley.net) is that i have my domain which is called mbentley.net. in DNS, i have a record that points to the IP address of mbentley.net that way my web site works. another thing you could do is make it so your domain is actually a subdomain of "ocfkicksbutt.com". you could assign the domain as something like "ads.ocfkicksbutt.com" and then ocfkicksbutt.com would work fine.

Mr.Guvernment
07-14-09, 12:57 AM
ya, good thing i learned before that, i am going to go with the .local ext and not worry about problems :)

ya i thougt about using a sub domain, would work good, for many thing i can think of but for now, i figure easiest solution is to do a diff .* and be done with it


the process of trial and error, glad i figured this out now!~

mbentley
07-14-09, 08:36 AM
actually, just to clarify my post above about adding a DNS record for mbentley.net, i actually added a record for "www" so that "www.mbentley.net" went to my external web host but requests for "mbentley.net" still went to the domain controllers as they should.

SuperMiguel
07-14-09, 09:01 AM
thats what i do on mine.. server.supermiguel.com

RJARRRPCGP
07-14-09, 11:28 AM
I have set up 2 Domain controllers with AD and DNS (DC01 and DC02)

Now if i set my desktop system to use either DNS server, some websites, well 1 specifically, cant be viewed, IE seems to instantly say:


Internet Explorer cannot display the webpage

What you can try:
Diagnose Connection Problems

More information

This problem can be caused by a variety of issues, including:

•Internet connectivity has been lost.
•The website is temporarily unavailable.
•The Domain Name Server (DNS) is not reachable.
•The Domain Name Server (DNS) does not have a listing for the website's domain.
•There might be a typing error in the address.
•If this is an HTTPS (secure) address, click Tools, click Internet Options, click Advanced, and check to be sure the SSL and TLS protocols are enabled under the security section.




This is a default installation of a DNS server, no changes or modifications have been done to it, so far it only does this with 1 single website, all other sites work perfectly fine... I have tried it on 3 different computers all with the same result.

any thoughts?

That error can mean anything. That error from Internet Explorer is generic.

mbentley
07-14-09, 11:32 AM
That error can mean anything. That error from Internet Explorer is generic.

which in this case it was that it resolved the website to the domain controller which does not appear to be running a website. ;)

Mr.Guvernment
07-17-09, 07:07 PM
Correcto! :)

is now fixed, labeled the site with .local instead.