Topic: DNS settings - need to resolve 1 domain through specific DNS server

[senti]

Setup is very simple.

I have local domain setup (let's call it "localdomain.com", and SME 7.4 handles it nicely).

However, I have a need to resolve another internal domain (we'll call it "internaldomain.com"), via other DNS server, located at 10.1.1.1.

Is there a way that SME resolves everything on its own (resolving localdomain.com and all requests for other domains), but to resolve that internaldomain.com using 10.1.1.1?

I have tried adding 10.1.1.1 as a "Corporate DNS" then assigning it to internaldomain.com in web interface, but it ended up being used for all queries coming to SME.

It also seems that manually modifying /var/service/tinydns/root/data doesn't help either, since it gets overwritten on tinydns restart.

Any help is much appreciated.

Thanks.

[senti]

Even tried doing:

db configuration setprop internaldomain.com Nameservers 10.1.1.1

Then tried signal-event dns-update (with and without domain name added).

Doesn't even try to resolve it now, I don't see any traffic going out on any interface when client sends a request for internaldomain.com, SME immediately returns 'not found'.

[senti]

Even tried doing:

db configuration setprop internaldomain.com Nameservers 10.1.1.1

Then tried signal-event dns-update (with and without domain name added).

Doesn't even try to resolve it now, I don't see any traffic going out on any interface when client sends a request for internaldomain.com, SME immediately returns 'not found'.

Oh well, replying to myself - seems like this command is correct one to use:

db domains setprop internaldomain.com Nameservers 10.1.1.1

So, if anyone has the same problem, hope this helps.

[CharlieBrady]

Oh well, replying to myself - seems like this command is correct one to use:

db domains setprop internaldomain.com Nameservers 10.1.1.1

The above command will only work if there is a record internaldomain.com already in the domains database. You would create that record using the domains panel. Note that there still could be some problems with this configuration - e.g. server will attempt to deliver mail to person@internaldomain.com locally, rather than to use MX record published by DNS at 10.1.1.1.

[senti]

The above command will only work if there is a record internaldomain.com already in the domains database. You would create that record using the domains panel. Note that there still could be some problems with this configuration - e.g. server will attempt to deliver mail to person@internaldomain.com locally, rather than to use MX record published by DNS at 10.1.1.1.

Yes, domain was already in domain database.

I only need it to resolve some A records, mail delivery is taking completely different route.

Thanks

[CharlieBrady]

Yes, domain was already in domain database.

I only need it to resolve some A records, mail delivery is taking completely different route.

You haven't understood what I told you. Mail delivery from the SME server itself to this particular domain (if there is any such mail) will not work.