Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
i didnt get it correct,but to my knowledege we need a software like ddclient to update ip information in the server
dyndns.com have a reference page of using this perl package
regards
Tom.
Thanx!!! It worked for now. That is a temporary solution to my problem.
Let me be more descriptive:
I've got several FreeBSD vpn boxes at clients.
All of them connect to the internet via adsl.
The isp assigns random ip's to the FreeBSD pc's (41.241.11.119 - not actual ip)
I created a user account for each of the FreeBSD pc's.
They login to the mail server with cron jobs and fetchmail on a regular basis. So if one of the FreeBSD pc's gets a new ip assigned to them I'm able to check the log file on the mail server to see from wich ip that specific Freebsd pc logged in from.
I want to set up my own server to assign ip's to my several FreeBSD pc's. I assume a ddns server is the way to go.
If anyone has some pointers for me, it will be greatly appreciated!
I feel you are not describing what the problem is here. So you have a mail server, and you have freeBSD boxes that connect to it. The address of these servers change, but so what? They're connected to the net, and can reach your mail server, then what is the problem?
If you always need to know the IP of these remote boxes, why not use the aforementioned cron to have them sign into the mail server every 5 minutes? That way you always have their IP address, and you should be able to connect to them.
DHCP wouldn't server any purpose. You could assign an address to the VPN clients, but don't they already have a LAN address through the VPN?
I'm not making much sense out of what you're trying to accomplish here. Where does ddns even factor in?
Please write back and explain what you need to have happen.
I've got a registered domain mycompany.net with a static ip.
The FreeBSD boxes get random ip's from my isp.
What I want to do is create subdomains for each FreeBSD box:
clientsite1.ddns.mycompany.net, clientsite2.ddns.mycompany.net,
clientsite3.ddns.mycompany.net....
Mainly I don't want to use dyndns.com, but want my own DDNS server.
I want to ssh to my FreeBSD box on clientsite1.ddns.mycompany.net and not the wan ip 41.242.3.66.
The FreeBSD boxes are used as vpn/firewall/routers.
There are several windows based pc's on site where other companies do support for the sales software and they use PcAnywhere.
Now every time these guys want to do support they first phone me for the ip of the FreeBSD box. I want them to use clientsite1.ddns.mycompany.net instead of the ip too.
What would the best route be for taking on this task?
Setting up a new DNS Server?
How?
Yes, you'll want to run your own ddns server, which is just a BIND dns server with a ton of keys for the remote hosts, allowing them to update just their specific subzone. As a partial example, clientsite1.ddns.mycompany.net would get one key, that allows it to update just the clientsite1.ddns.mycompany.net zone file. The main tools needed are the dnssec-keygen tool, which is a standard part of the BIND installation and also client install, and you'll need the nsupdate tool, so the clients can puch their changes to the nameserver. I googled (how to setup ddns server) and the most promising results were found here:
You'll have to cron the updating I would think. and you'll also have to use the dnssec-keygen key to allow the clients to refresh the zone once they edit it. You'll have some permissions to mess with, and be certain BIND on the static box is running as user named or bind, not root, or you'll be exploit heaven.
Now I know where to start.
I'll let U know how it goes.
Just a matter of interest:
I want to use SLES10 but my boss wants me to use FreeBSD V6.
What do U prefer?
I'll end up using the FreeBSD anyway but I'll try SLES on the side to.
I would never use Suse for any reason under the sun. I think all rpm based disros are crap, and are virtually windows-lite. Since Suse cut their deal with Microsoft, most people avoid them like the plague.
I agree with your boss 100% BSD is a very secure system, and ideal for doing things like this.
I would never use Suse for any reason under the sun. I think all rpm based disros are crap, and are virtually windows-lite. Since Suse cut their deal with Microsoft, most people avoid them like the plague.
I'm almost done.
I've got other projects to take care of to,
but haven't given up yet.
I'll finish it over the weekend or so and when it is fully functional I'll post a Howto for all the newbies out there like me!
Since it seems to be complaining about the key, I'd start there. Are the keys identical? It would also be worth it to generate a new key and try that out if an md5sum on the keys does come out to be identical.
Also, another good reason to do that is you published here what the secret key is. This string, WNmmnCCJ9VvzQosdrYOspQiOp02LxtPUlNAqAUbB/l2SBzsblfkl+1q7 t1+ZYS6rbEub0kJ5ejRwGxm6CGwvFA==, should be kept hidden. With that string you can insert false data into your DNS record, should somebody want to.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.