View Single Post
  #10  
Old 25th October 2005, 11:17
falko falko is offline
Super Moderator
 
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 41,701
Thanks: 1,900
Thanked 2,735 Times in 2,571 Posts
Default

Quote:
Originally Posted by Lil'Brudder
I'm assuming that if I can get GoDaddy to accept my DNS, my server will be able to resolve all the A/MX/etc records and everything will be fine... is this not right?
Yes, that's right. You have to make your nameservers authoritative for your domains.

Quote:
Originally Posted by Lil'Brudder
I have port 53 forwarding to the server, is this the correct port?
Yes, but it's port 53 TCP and UDP!

Quote:
Originally Posted by Lil'Brudder
Also, I noticed there are 3 other ports open:

Port 5335 (tcp) is open (unknown)!
Port 32769 (tcp) is open (unknown)!
Port 55512 (tcp) is open (unknown)!

Are these used by ISPConfig? Do I need to have them forwarded in my router also? Or can they be left alone?
No, these ports aren't used by ISPConfig. I don't know what's running on these ports, so if you don't know this either, you should better close them...

Quote:
Originally Posted by Lil'Brudder
*Edit*
I just noticed... the IP address is wrong in that Bind file. That's the IP of where the server *will* be... it's on a temporary IP right now. Is that why Godaddy isn't resolveing ns.liquidlightning.com?

If I change that to the temp IP, would that fix it?
*Edit*
Hm, I think you should contact the GoDaddy support about this... - or just try.
__________________
Falko
--
Download the ISPConfig 3 Manual! | Check out the ISPConfig 3 Billing Module!

FB: http://www.facebook.com/howtoforge

nginx-Webhosting: Timme Hosting | Follow me on:
Reply With Quote