Well technically doesn't always work but we'll see. I gotta download some client which will update up to 5 dynamic IPz. I'm using Verizon DSL and don't wanna invest more money on this but if i need to buy static IP maybe i will cuz i wanna be sure my page is 99.99% online .

I guess that should be more than self explanatory, however as you said it so it might be another marketing trick , i'll let you know. First i need to get somebody on the other side, when i get the reply and after my domain is delegated i'll let you know if it's possible and how stable it is.

Sorry the quote cut the full content.

I'm not sure I see the point to having myname.com with a dynamic IP. There are sometimes delays as your IP address gets updated in the system. This is fine for personal use, but not if you expect to have regular visitors. On the other hand, if your server is for personal use, why not just use myname.is-a-geek.com (one of dyndns domains)? I know this is a little different if you shell out some money to your ISP to claim a static IP. But still...

An i got something like help from them.

Right on man if that's tech support i might be a bus station or something. I guess i have to figure it out myself.

btw Slackware was established 1991 as far as i know so what 14 years is this guy talking about i don't know .

moger

If you have a registered domain name your only problem is your dynamic IP

Reverse DNS is as you quite rightly say is owned by your ISP but that at least for me does'nt present a problem

I have a web site on my home PC and use a utility to update my IP at dyndns.org should it change, which has'nt happened in the last 12 months

Pete

So far so good but why?
When you place an order @ DynDNS for Custom DNS service and you purchase a domain from there say mydomain.com they log your ip. When the service is active, just by typing in a browser www.mydomain.com it will connect straight to your server(the IP which was logged) as long as you are running the box with the appropriate services eg. apache/php/mysql etc. However, the question remains: Am i supposed to netconfig and put whatever for host and for domain: mydomain.com, or what i saw so far in other post is is that the domain might be set to dyndns.org and the host is yourusername.mydomain.com. I'll post some updates when i found out the truth behind this mistery . I hope that won't be another X-File.

laterz

If all your doing is running a webserver, I don't see any reason to change your host or domain names. I renamed my host and domain so that mail from my email server made sense. I prefer not having my email headers say something like "from: user@adsl-255-255-255-255.sbcglobal.net". I believe there are other solutions using the Sendmail configuration file, I just prefer mine.

I think that if you try setting up a mail server and read all of your headers, it will all start to make sense.

The problems is i wanna run mail server two with the appropriate emails say sales@mydomain.com or support@mydomain.com and i keep on getting the same error message on the sendmail configuration that my host cannot be resolved. Still searching for a solution though. There is nothing so far. The worst thing is that even the dyndns.org support gang doesn't help at all. So it's till a mystery how to netconfig the machine and how to get the sendmail working. If anything i'll let you know cuz so far it's quite of a bummer so i would like to share my experience as soon as i see wazup with that.

laterz

Here is a little trick that has worked so far.

First I use a adsl provider that will "lease" you a fixed static IP addy for $14.00 a month.
Second I have 2 registered domain names "parked" at godaddy.com @$7.95 per year till 2006.

Ok here is godaddy.com services.
1) 100 names email forwarding each domain
If you are running a e-mail server you can point these to your addy if you have set the servers up properly. example "user@123.123.123.123". You can also set up pop3 services as you have a resolvable addy.
You must have ports 25 and 110 "triggered" through your firewall. Do note be sure to set up proper security to avoid becomin' a "zombie" relay for spammers

2) Domain name forwarding from "parked" domains
you can forward "point" the domain names to your own servers in the same fashion as the e-mail above by entering the addy in the provided form at godaddy "manage domain" section.
In your firewall be sure to point port 80 to your webserver.
Also you can configure apache for virtual hosting of multi-domains to handle in bound forwards.

3) godaddy provides another service I have not tried as of yet which is a "private based" nameserver link. They have help files for this and a full auth server is required on your end.
I run a fully qualified DNS server auth for my network.

Now I know this does not note linking a dyn-dns set up. But I think with a little experimentation (like I did) a dyn-dns user should be able to trick up the same working set up.

Some hints.
a) You may have to write or hunt down a script to do some automated linking.
b) It may be possible to link a host name with the dyn-addy at the dyn-dns provider and then have this host name link at a service like godaddy.
c) Not real sure if this will "by-pass" ISP snooping for TOS violations (running public services)
which with a little creative route and firewall editing it "may" be possible to point their "snoop" servers to "special" ports (also a TOS violation on most providers).
d) Some providers frown on "any" service or server running on a provided connection that is not a "business" account, read more $$$. However reading the TOS "seems" to indicate that mail servers are tolerated as long as they are not for "public, spamming or questionable" uses. Many really frown on proxies, keep-alive scripts (<automated, dial-ups) and webserver.
e) If your ISP "snoops" your service and freezes you out just annie up some more change ($$) to them and go legit. Most ISP business services are $10 to $20 usd over what you are probally payin' now for you connection (adsl) plus you get added bonuses like ISP provided DNS, multi-static IPs and may be worth it.

vaworx

Sendmail will only send and receive mail for a FQDN ( fully qualified domain name ) on start up it checks etc/hosts for the domain it is responsible for

I can only quote on Redhat but here is my etc/hosts, server is the my machine name

127.0.0.1 server.mydomain.net server localhost.localdomain localhost

You also need to edit etc/sysconfig/network again here's mine

NETWORKING=yes
HOSTNAME=server

I think you are using Slackware but this may help

Pete

Yes you must have a "resolvable" host.domain.name for sendmail to work properly.
However this address can be a local "private" address (say in the 192.168.0.0 range) it does not have to be a "world" net address.
The /etc/hosts file can be used as the DNS provider for local look-ups

Here is a correct example of this

# etc/hosts

127.0.0.1 localhost # note it is advised NOT to assign a name.domain to the localhost addy
192.168.2.10 mycomputer.mydomain.myinitials mycomputer mycomputeralias mycomputertoo
192.168.2.11 myothercomputer.mydomain.myinitials myothercomputer myothercomputeralias

Explained:
the 192.168.0.0-192.168.255.255 is a reserved IP range for private addresses

The first (mycomputer.mydomain.myinitals) is your computers hostname and domain you assigned it when you did the install or later. It is common to use something other than .com, .net -etc as the last domain segment
The names follow the first portion (mycomputer mycomputeralias) are other names associated with your machine or alternate spellings there of.
You repeat this for all your boxes you have ASSIGNED addys for.
Note even if you are dial-up it is a good thing to assign a local addy.

Now for sendmail to do its magic it will but you should do a bit of configureing in the /etc/sendmail area. Read before you hack any of these files!!! See the HOWTOs...

Muhahahahahah,
sorry can't help myself the bugga is finally working and is running up and stable. That took some time yeah i admit but looking at the result right now i'm more than happy. K so pretty much after getting the Apache+PHP+MySQL+OpenSSL running one thing was missing and of course as i mentioned above this was the Sendmail configuration. After following Shilo's web howto i got it running. I'm using Verizon DSL so i used outgoing.verizon.net for the outgoing server in sendmail-slackware.mc. After doing everything necessary i keep on getting the same error get getdomainbyaddr failed: 1. Why cuz i was stupid enough to not put mydomain.com mydomain in the /etc/host file so pretty much it looks like this:
The last one is because like any other i'm using the same machine as router/firewall (planing to get something cheap btw and try the monowall). Anyways so i fixed that problem but the next obstacle was: that was of course something that took a while to figure out while it was sooooooooooo simple but who reads the manual .
By default it should be empty so you need to add first the main domain, then the host and the domain:
Of course that means that you will be able to get emails from both user@mydomain.com as well as user@myhost.mydomain.com
The last but not least . Log on to DynDNS with your account and ADD MX Entries for the things that you just did.
Click on Add New MX -=> Leave host field empty -=> Leave Preferences to 5(Highest) -=> type in Mail Exchanger mydomain.com. Once you are done click on Add New MX again and do -=> Host: myhost -=> Preferences: 10 -=> Mail Exchanger mydomain.com.

I hope i didn't forget or misspelled anything. Something i lost a lot of time was following the instruction in the sendmail conf files DO NOT FOLLOW THOSE INSTRUCTION IF YOU ARE NOT SURE WHAT YOU ARE DOIN' -=> Better follow Shilo's manual.

that's about it.

laterz

BTW the solution i mentioned above is for the general problem most users get while setting up sendmail.
.

mmmmm yeah that's about it if any suggestions or concerns feel free to criticize