![]() |
DNS configuration in ISPC 3 - please please
I need some help for setting up DNS with ISPConfig 3 please.
Here is the situation: Quote:
Server2 should be reachable at http://server2.host.com, and the DNS server should listen on both IPs: IP1: 219.152.248.132 -> dns3.host.com IP2: 219.152.242.245 -> dns4.host.com I did insert some A records on Server1: server2.host.com -> 219.150.248.132 dns3.host.com -> 219.152.248.132 dns4.host.com -> 219.152.242.245 (those changes were successful, all three point to the new server) Is the above correct? What do I need to do on server2? Many thanks for help, I am not good at that. |
It looks good. You were correct regarding adding server2 to server1's ns servers as server1 holds the zone for host.com...lots of people miss that point.
You will have to allow zone transfers between server 1 and server 2 if you plan to use server 2 as a slave to the primary ns server. Its done in the zone section of DNS however I have not played with it yet on version 3. a. |
Well, yes, I got it that far...
But then I don't know what to do on the ISPC3 server. (I do not plan to run it as a slave) Should server2 acknowledge somehow that it is indeed dns3 and dns4? I tried to setup a domain on ISPC3, but it doesn't work. I must be missing something. On server2, I setup a zone: Quote:
then I setup records in the next tab: Quote:
even if I try nslookup on the same server the domain is hosted on, it won't find it! can you spot the fatal error? |
If you wnat to setup a domain in the dns manager, then use the dns wizard to get an idea how the correct records shall look like.
Quote:
Quote:
Regarding zone transfer. In a dns server setup that uses mydns in most caeses you use mysql replication or let all dns servers connect to a central database instead of using zone transfer. |
Thank you.
I do not intend to do zone transfers. I used the wizard and corrected the entries but still no joy. Here is how they look now: Quote:
Quote:
EDIT: I just ran an external test and it said: Quote:
|
The record looks ok now. How did you test it? You must be aware that chnages in dns take up to 48 hours to become valid!
If you wnat to test it now, use the dig command on the shell like this: dig @localhost mydomain.com |
Thank you very much Till, it is working now!
|
| All times are GMT +2. The time now is 11:09. |
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2013, vBulletin Solutions, Inc.