Avatar of Frank Ferrer
Frank Ferrer
Flag for United States of America asked on

cannot access previously accessible website dns error

We are having a problem on our domain accessing a website we normally had access to. Our network has several sites and each of our sites has a domain controller and dns server. We have one main fsmo server at our corporate office.

When I am not connected to our network (using aircard or home connection) I can easily get to https://intranet.artizan.com    As soon as I am on our domain or connected to VPN (that our ISP hosts) I am unable to connect. I should note that when users connect to vpn it is set to static our fsmo server's IP address so users can access network shares, etc.
I spoke to our ISP and we did tracert tests to 204.155.61.221 it went through all of our ISP's routers and then hung up right before getting to to their site. The next thing I did was to hook my computer up to our network and then I staticed our dns settings to google's dns (8.8.8.8 and 8.8.4.4) so I could bypass our dns server.....when I did a ping to intranet.artizan.com it resolved the IP (204.155.61.221) but I still got a reply timed out.
anything that I can do to make this work like it used to? I can see this maybe being an issue on the server that we're trying to get to..perhaps it doesn't like the public IP we use to connect to it? Strange that we were able to reach this website just fine and then all of a sudden we can't.

Any suggestions would be fantastic. Thanks! I'm not an expert on root hints, conditional forwarders, etc. so any help is much appreciated!
DNSVPNInternet Protocols

Avatar of undefined
Last Comment
Steve

8/22/2022 - Mon
SOLUTION
Steve

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
gheist

dnssy.com says:

NS records at parent nameserver:      Your NS records at your parent nameserver are:
Provided by a.gtld-servers.net -> ns1.applieddns.com
Frank Ferrer

ASKER
thanks dnssy.com and totallytonto. Our internal AD domain is not relateed to the website we are wanting to reach. It is just a site that used to be able to reach. We use internal DNS on our Active Directory domain, i.e. we static each branch's dns to our fsmo server and then to itself. Not sure if the comment above applies to us. Are you saying to point our dns servers to the name servers above? that would affect anyone trying to get our internal dns to work, correct? Thanks.
ASKER CERTIFIED SOLUTION
Steve

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
All of life is about relationships, and EE has made a viirtual community a real community. It lifts everyone's boat
William Peck