![]() |
does not answer
Hi,
I have done installation om debian Lenny, and all works fine, and use another server to resolv. A have a test domain.com and i have point the domain to my servers IP address, and configure mydnsconfig to act as a master DNS for my domain.com i have put up a web server and mail server om another IP. If i try dig and nslookup i got no response from the server, im sure my router i configure correctly. i have no ide whats wrong and cant fint any error messages i the log files. |
Please post a screenshot of the domain settings in mydnsconfig for this test domain (the first tab and the records tab).
|
file
1 Attachment(s)
as requested
This DNS server has IP .60 at the end. |
file2
1 Attachment(s)
as requested2
|
The zone tab is ok.
|
You missed to add a dot at the end of the fully qualified domains names. In mydns and BIND, records that contain a fully qualified domain have to end with a dot.
The zone tab is ok. |
file3
1 Attachment(s)
it this the correct settings?
|
No. You missed to add the dots in the fqdn's in the data field. Something like ns1.domain.com is a fqdn (fully qualified domain name) and a fqdn has to end with a dot. So it must be ns1.domain.com. and mail.domain.com.
If you have relative records like "www", there is no dot at the end. For example, your current MX record mail.domain.com. points to mail.domain.com.domain.com as it is currently a relative record and not a absolute. I guess what you want is that emails for ...@domain.com gets delivered to the server mail.domain.com, the record for that will be: name: domain.com. data: mail.domain.com. |
file4
1 Attachment(s)
yes you right, i hope i correctmy mistakes
|
Better but not fully correct. Please see what I posted above for the mx record. Data must be domain.com. and not mail. Otherwise you would be able to get only emails for ...@mail.domain.com but I guess you want to get emails for ...@domain.com
The ns record is fine. |
| All times are GMT +2. The time now is 15:20. |
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2013, vBulletin Solutions, Inc.