DNS Crashed, Sharepoint no longer loads

[Psymon]

DNS went tits up the other day and after reacreating the zones ive had problems with the sharepoint site.

 

MIS came back up fine, outlook web access still works, outlook started working once the MX record was created etc... however our sharepoint site has the following page when loading straight from IIS with right click -> browse (attatched)

 

Anyone seen this before?

 

Si

[webman]

Check the DNS host record for your Sharepoint site is exactly as it should be.

[Domino]

well in the screenshot it looks like the sharepoint site isn't running...

[Psymon]

Check the DNS host record for your Sharepoint site is exactly as it should be.

 

as in sharepointname.domain.org.uk point to the server ip addy?

 

and the live sharepoint site is called DCNet and is running.

[webman]

as in sharepointname.domain.org.uk point to the server ip addy?

 

and the live sharepoint site is called DCNet and is running.

 

Yes, that one. Also, is the Sharepoint site still configured to respond to requests for "sharepointname.domain.org.uk"? Have you checked the event log for any obvious errors generated by IIS/Sharepoint at the times when you try to request the site?

[Psymon]

No way, i tried that yesterday and it didnt work so i deleted the record again thinking it was too simple.

 

Thanks for your help!

 

The only other wierd thing is (due to a single external and internal dns name) i cant access our outlook web access from internal (same DNS name)

 

https://mail.domain.org.uk/exchange

 

Externally fine, internally i get a website not found. (just thought an A record pointing to our external IP should do the job)

 

Sorry for 2 questions in 1 post

 

Si

[jamesb]

If you use the IP address rather than the URL, can you browse to the site successfully?

[webman]

The only other wierd thing is (due to a single external and internal dns name) i cant access our outlook web access from internal (same DNS name)

 

https://mail.domain.org.uk/exchange

 

Externally fine, internally i get a website not found. (just thought an A record pointing to our external IP should do the job)

 

Sorry for 2 questions in 1 post

 

Si

 

Not sure on the Exchange bit to be honest. I would have thought that internally, mail.domain.org should resolve to the internal IP address; but I don't know what effect this has on the HTTP SSL aspects of it.

 

The only reason I see you wouldn't be able to do this, was if your DNS servers respond to requests from the outside world (eg. give the external IP address).

[Psymon]

No luck.

 

If i go to https://localhost/exchange on the exchange server it loads, externally (outside of the domain) it loads.

 

Single DNS name is a pain

 

DNS servers dont talk to the outside world, we contact our ISP / Host and get them to publish the records for the ip adresses we own.

 

Wierd.

[jamesb]

I take it you've flushed the DNS cache on whichever system you're using?

[Psymon]

yea "ipconfig /flushdns" did the job for the sharepoint.

 

Si

[Psymon]

All works as intended now. Thanks for all your help.

 

Simon