Re: systemd-resolved, split dns, & vpn setup

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I'm answering this with a separate response because it goes off in a
different direction.  You can decide which way to go without mixing up
all the information together.

On Sat, 2021-04-10 at 12:03 -0700, Jack Craig wrote:
> I think I understand that the primary name server for domain must be
> in my case this home server that I'm using and that I need to be able
> to resolve my service name to my service public IP based on a
> mechanism that I expected I provide through find 
> 
> what seems to be happening is that I am not getting external and
> internal resolutions for internal and external look ups
> 
> AT&T my ISP has agreed to secondary my DNS server but I'm expecting
> to set up the primary so it is setting up that primary and
> coordinating it with the external IP look up's from the world that I
> am stumbling on at the moment

In very few cases the primary name server for a public DNS record will
be on a home computer.  It'll usually be done where you register your
domain name.  Though you can shift it elsewhere.  You can renew a
domain name and host it with a different company.  You can have a
company host your website, and they can also host your DNS records.

For what it's worth, if they do your mail and website through something
like cpanel, they'll probably want to host your DNS records, too, so
their cpanel software can control any changes the DNS records.

You can run your own slave name server, that follows what the public
one does.  This can be handy, but not essential, to keep an eye out for
anything that goes wrong.

If you want to run dynamic DNS, so you can log into your home computer
from somewhere else on the net without having to know your IP, that's a
different thing, again.

But, if you want to be your DNS server for the whole world, they have
to be able to connect to you.  Traffic has to be able to get through.
 And you will need a fixed IP.

_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux