DNS not aliased for "Domain Pointers"

R

roop

Verified User
Joined
Feb 10, 2007
Messages
7
Hi All,

I've got a major problem with DNS for domains that are set up using as "Aliases" to allow DA to handle the DNS.

EG: domain.com is main with it's own account, and custom DNS records such as test.domain.com resolving to 127.0.0.1, mx records set to use another server, as well as the default www/ftp DA records resolving to the local DA machine IP, eg 123.123.123.123

Once the domain.com account is created, I went to the user control panel, clicked "Domain Pointers", typed in domain.co.uk as the source domain, made sure the "Create as an alias" box was ticked, and clicked Add. domain.co.uk is now listed as an alias.


www.domain.co.uk resolves correctly to 123.123.123.123, but test.domain.co.uk doesn't resolve to 127.0.0.1 (or anything else!). Upon further investigation the zonefile for domain.co.uk just contains the default DA zone info, and none of the changes made to domain.com's zonefile.


I don't really understand why this is happening, and would have expected "Alias" to mean all services including DNS. Does it perhaps _just_ affect httpd? If so is there any way to get my aliased DNS zones to work properly or do I have to type all the changes in again and again ...?


Yours hopefully,

Roop!
 
Hello,

Subdomains were never part of the domain aliases.
If you want test.domain.co.uk, then you'd just add another domain alias called test.domain.co.uk, and it would point to your main public_html folder.

As for subdomains, this upcoming release will support them:
http://www.directadmin.com/features.php?id=798
**However** the dns portition will still not be setup due to load issues in doing it with remote clustered dns servers (explanation in the guide).

Any dns setting you wish to have in the domain pointer, just add manually, or alternatively, just add a wildcard *, which will cover you for all future subdomain additions.

John
 
Excuse me for getting things mixed up but in my last post I was solely talking about the MX-entry.

The thing is, that I have a customer who has his own Exchange Server which I pointed to by changing the MX-entry and deselecting the 'handle mails locally checkbox'.

At this moment I'm engaged in transferring 18 other domains of his to 'my' server. These domains need to be domain pointer aliases since the main domain has a script that acquires the HTTP_HOST var for content purposes.

I did set the right MX-entry for the aliases but these seem to ignored because these domains are handled locally by EXIM.

I've asked the serveradministrator to check if these aliases exist in etc/virtual/domains. If so their deletion from etc/virtual/domains would mean they would be handled externally, or so I think.

The above seems to have been addressed in http://www.directadmin.com/features.php?id=365 but it doesn't seem to work, unless this was solely ment for 'pointers' and not for 'pointers created as aliases'.

Kind regards,

FurieZ
 
Correct... however the addition only works for newly "unchecked" settings.
Bascially, if it's currently unchecked, check it, save, then uncheck again, and save to get the pointers out of the /etc/virtual/domains file.

John
 
You must log in or register to reply here.
Back
Top