Topic: Tiny DNS need help

[Frustrated]

Need help how to use the tinydns dns-server of SME 6.0.

My domain is mydomain.net and i need a dns-entry for everything.someoneelses.net to a external ip-number (not on my domain).

The use of a virtual domain in the server manager is not applicable since it's not my ip i want them to go to.

Thx!

Richard

[Guest]

Am I alone on this one?

Nobody knows about tinydns?

[gbaird]

Read the book

You want to forward to a remote ip for
everything.someoneelses.net

make a virtual domain the go to the hostnames & addresses screen
you can set the ip for any thing or where you want
just buy clicking on the modify link

create the someoneelses.net domain then in the hostname screens
create the hostname everything.someoneelses.net and point it to the other ip address - any hostname can be pointed somewhere else mail = 192.168.1.2 www = 192.168.1.3 ftp = 192.168.1.4 etc

it is pretty simple once you understand the basics

[Richardo]

Gbaird, thanx for replying.

I know how the virtual domains works. The thing is, I don't want to use a virtual domain since I don't have enough control. Also I don't want to change to many configuration files (samba,qmail,squid) on my server, because it will only make things messy.

For example, all the mail-aliases are made (allmyusers@virtualdomain). Using a virtual domain will also block any future real dns entries for the enire domain. I just want to name a specific hostname, simple as that. Also, some virtual names are not possible (there is always a www. upfront).

The only thing I want to adapt in my DNS is:
work  :   192.168.0.1
(and not www.work)

If a add an A hostname in:
/etc/e-smith/templates/var/service/tinydns/root/data
then
/sbin/e-smith/expand-template /var/service/tinydns/root/data
/sbin/e-smith/signal-event domain-create
(for updating the tinydns and dns-cache)

this doesn't do the trick...
clients and server don't know about the new entry.
What am I doing wrong???

Any help appreciated.

Richard.

[gbaird]

hello

I don't know what you are trying to get done

changing dns records by hand you need to know what you are doing

virtual domains are not a problem and you have full control

again if you explain what you are trying to get done I maybe can help

Samba is not affected by dns or any outside network it is mainly for you local area network unless you are setting up ptpp

if you want a specfic hostname that is different that a domain name you really need to read about networking

on your sme box on the host name page take a look

www is there so is mail & ftp but if you want to add a hostname you can it is not or does not affect anything else

samba.domain.com  or
different.domain.com

you have not said what you want to really do last post was change a port number the ip address is all you need to deal with

are you trying to run 2 web servers or what are you trying to do? iis doesn't have a mail server so what is the virtual domain problem again you need to read about networking it will simplify the approach you need to take

[Guest]

Here's the deal:
Sme server1: www.domain1.com
Sme server2: www.domain2.com
Both domains are registered domains and have services running webpages, mail etc.
They are connected through ipsec vpn.

What I want is to manually change the local resolvement of an external domainname to get the traffic through my vpn-tunnels. However, www.domain1.com resolves into the external ip.

Adding a virtualdomain domain1.com on domain2.com will affect more than I want to establish.
i.e. mark@domain1.com now equals mark@domain2.com
Again, domain1 and domain2 are existing registered domains.

If I can manually add a dns entry called 'domain1' or 'secure.domain1.com' to the internal ip, I'm finished.

Thx!

[CharlieBrady]

Need help how to use the tinydns dns-server of SME 6.0.

I don't think you do.

My domain is mydomain.net and i need a dns-entry for everything.someoneelses.net to a external ip-number (not on my domain).

This is a job for the DNS admin of someoneelses.net.

[Anonymous]

Charlie,

The DNS admin of someoneelses.net is a SME server as well.

Anybody a clue, how to put tinydns to your hand?
Somehow, the implementation seems different from the howto's of a 'normal' tinydns config.
http://tinydns.org/

[hardijs]

Gbaird, thanx for replying.

The only thing I want to adapt in my DNS is:
work  :   192.168.0.1
(and not www.work)

If a add an A hostname in:
/etc/e-smith/templates/var/service/tinydns/root/data
then
/sbin/e-smith/expand-template /var/service/tinydns/root/data
/sbin/e-smith/signal-event domain-create
(for updating the tinydns and dns-cache)

this doesn't do the trick...
clients and server don't know about the new entry.

did go through the same until I realised that tinydns "consists" of 2 parts.
You need to tackle the dnscache as well

/var/service/dnscache has a servers dir which has to contain "work" file with "127.0.0.1" content
I do presume (just deduction w/o man page reading) that it tells dnscache which domains are to be resolved where.

I did and it works for me.

now any client on local net is able to connect to "work" unless dns is not pointed to sme.

  - no more hosts file editing (and hosts file did not work anyway - squid got involved which ignored my feeble hosts file editings)